home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Aminet 8
/
Aminet 8 (1995)(GTI - Schatztruhe)[!][Oct 1995].iso
/
Aminet
/
comm
/
fido
/
Rock_1_5.lha
/
ROCK
/
LaunchWPL.DOC
< prev
next >
Wrap
Text File
|
1995-04-22
|
2KB
|
64 lines
LaunchWPL.DOC
Robert Williamson
LaunchWPL is a combination of the original LoadScript and Launch WPL
commands. It is intended for use with single module wpl mailers such as
Pop by Denis Turcotte, JamMail by James McOrmond and Jaz by myself.
To load and launch a wpl program:
LoadWPL <scriptname> <fullpathname> <portname> <script!label> <priority> <stack>
To flush a wpl program:
LaunchWPL <scriptname> ""
Much of the remainder of this doc was derived or modified from
messages and documentation by Russell McOrmond.
LoadWPL tells wpl.library to load the file named in <fullpathname> and
bind this to the name <scriptname>. The scriptname is then used to
reference this script in Launch, SubJump, Post/Preinbound/Outbound labels,
and of course other 'loadscript' references.
The <portname> must be a *UNIQUE* message port name. A recommendation is
for all WPL application developers to adopt a system where they include the
name of their application in the name.
The <script!label> is the label at which the slave is started. The label
is normally 'startup'. You'll notice that it has the <scriptname> in
front. If the system does not specify the script name then it will
reference 'the first script loaded'.
The <priority> is the process priority for the wpl program.
The <stack> is the process stack size in bytes (Make sure this is fairly
large).
Note that doing a 'LaunchWPL' on a script that has no current users will
cause it to RE-LOAD that script into memory. If there are any users,
however, a re-load of a script will FAIL.
If a LaunchWPL is issued with only the <scripname> and there are no
current users, it will be flushed from memory.
LaunchWPL <scriptname> ""
Return Codes:
Load Flush
0 - All OK so far Flushed OK
1 - Can't create public port --
2 - Can't open timer --
3 - Can't allocate vars structure --
4 - Can't open xferq.library --
5 - Error loading <fullpathname> Unable to flush
99 - No memory in slave --
101 - No memory for structure --
102 - Error in new process launching --
666 - Unable to open wpl.library same
999 - Invalid number of arguments same